Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1809

reference: 278-tree-1
name: 1809
tree-preservation-order: undefined
278-tpo-1
uprn
address-text
point: POINT (-0.979082 50.859141)
geometry: MULTIPOLYGON (((-0.978983 50.859131,-0.978987 50.859150,-0.979001 50.859168,-0.979023 50.859182,-0.979050 50.859191,-0.979081 50.859195,-0.979112 50.859192,-0.979140 50.859183,-0.979162 50.859169,-0.979176 50.859152,-0.979182 50.859133,-0.979177 50.859113,-0.979163 50.859095,-0.979142 50.859081,-0.979114 50.859072,-0.979084 50.859069,-0.979053 50.859072,-0.979025 50.859080,-0.979003 50.859094,-0.978988 50.859111,-0.978983 50.859131)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL